Thanks, I checked this out locally and I still see the 404 in the example you updated.

Thanks, I checked this out locally and I still see the 404 in the example you updated.

Hmm, it works for me. I look more into it

Thanks, I checked this out locally and I still see the 404 in the example you updated.

@john-griffin could you give it another try?

Still a 404 with that pattern. I'm running via the npm run dev command if that makes any difference, not npm run start-with-adapter

Still a 404 with that pattern. I'm running via the npm run dev command if that makes any difference, not npm run start-with-adapter

shoot! I'll take a deeper look at this over the weekend

So

Still a 404 with that pattern. I'm running via the npm run dev command if that makes any difference, not npm run start-with-adapter

turns out I was testing with ?inline which did not have?import prefix in some cases for some reason. this should now work as it matches both ?inline and ?import&inline and similar combinations

Thanks, that pattern is now working, imports are being returned with a 200 👍

Hey @barakcodes

Thank you for fixing. I've added the test for this change.

Looks good! Let's land it.